Controlling electronic devices using force sensors

ABSTRACT

Systems and methods for controlling electronic devices using force sensors include a plurality of force sensors configured such that they are operable to support one or more housings on one or more surfaces. When force is exerted on the housing, this force is measured by the force sensors as force data. This force data is interpreted as at least one input for an electronic device. In some implementations, the electronic device may include various different statuses. In such implementations, the status of the electronic device may be determined and the input that the force data is interpreted as may depend on the determined status of the electronic device. In various cases, the status of the electronic device may be a combination of one or more different statuses.

TECHNICAL FIELD

This disclosure relates generally to input devices, and morespecifically to using force sensors to control electronic devices.

BACKGROUND

Electronic devices (such as laptop computing devices, tablet computingdevices, desktop computing devices, mobile computing devices, cellulartelephones, digital music and/or video players, and so on) may beconfigured to receive input from one or more input devices. Such inputdevices may be external to the electronic device and/or may beincorporated into the electronic device. In many cases, such inputdevices require extensive hardware, special surfaces, and/or othercomponents that increase the cost of the input devices. Further,incorporation of many input devices into electronic devices may positionthe input device such that it is not usable during various states of theelectronic device (such as a laptop keyboard or track pad that is hiddenwhen a laptop lid is closed).

SUMMARY

The present disclosure discloses systems and methods for controllingelectronic devices using force sensors. A plurality of force sensors maybe configured such that they are operable to support one or morehousings on one or more surfaces. When force is exerted on the housing,this force may be measured by the force sensors as force data. Thisforce data may be interpreted (such as by one or more processing units)as at least one input for an electronic device.

In some implementations, the electronic device may include variousdifferent statuses. In such implementations, the status of theelectronic device may be determined and the input that the force data isinterpreted as may depend on the determined status of the electronicdevice. In various cases, the status of the electronic device may be acombination of one or more different statuses.

In this way, an input device that may not require extensive hardware,special surfaces, and/or other costly components may be provided.Further, such an input device may enable the electronic device itself tobe utilized as an input device.

Although the systems and methods are described herein as including forcesensors that are operable to support one or more housings on one or moresurfaces, it is understood that this is for the purposes of example. Invarious implementations, structures operable to support one or morehousings and/or electronic devices on one or more surfaces may not beutilized. Instead, force sensors may be located in such embodiments in abottom portion of an electronic device or housing, a top portion of anelectronic device or housing, a hinge between a lid and base of anelectronic device or housing, a specific portion of an electronic deviceor housing, and so on without departing from the scope of the presentdisclosure.

It is to be understood that both the foregoing general description andthe following detailed description are for purposes of example andexplanation and do not necessarily limit the present disclosure. Theaccompanying drawings, which are incorporated in and constitute a partof the specification, illustrate subject matter of the disclosure.Together, the descriptions and the drawings serve to explain theprinciples of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a bottom plan view illustrating a system for controllingelectronic devices using force sensors.

FIG. 2 is a side cross sectional view of a portion of the electronicdevice of the system of FIG. 1 taken along the line 2-2 in FIG. 1.

FIG. 3 is side plan view of an alternative embodiment of a force sensor.

FIG. 4 is flow chart illustrating a first example method for controllingelectronic devices using force sensors. This method may be performed bythe system of FIG. 1.

FIG. 5 is flow chart illustrating a second example method forcontrolling electronic devices using force sensors. This method may beperformed by the system of FIG. 1.

FIG. 6 shows a conceptual drawing of communication between a touch I/Odevice and a computing system.

FIG. 7 shows a conceptual drawing of a system including force sensors.

DETAILED DESCRIPTION

The description that follows includes sample systems, methods, andcomputer program products that embody various elements of the presentdisclosure. However, it should be understood that the describeddisclosure may be practiced in a variety of forms in addition to thosedescribed herein.

The present disclosure discloses systems and methods for controllingelectronic devices using force sensors. A plurality of force sensors maybe configured such that they are operable to support one or morehousings on one or more surfaces. When force is exerted on the housing,this force may be measured by the force sensors as force data. Thisforce data may be interpreted (such as by one or more processing units)as at least one input for an electronic device.

In some implementations, the electronic device may include variousdifferent statuses. In such implementations, the status of theelectronic device may be determined and the input that the force data isinterpreted as may depend on the determined status of the electronicdevice.

In this way, an input device that may not require extensive hardware,special surfaces, and/or other costly components may be provided.Further, such an input device may enable the electronic device itself tobe utilized as an input device.

FIG. 1 is a bottom plan view illustrating a system 100 for controllingelectronic devices using force sensors. The system includes anelectronic device 101. As illustrated, the electronic device is a laptopcomputer. However, it is understood that this is an example. In variousother implementations, the electronic device may be any kind ofelectronic device, such as a tablet computing device, a desktopcomputing device, a mobile computing device, a cellular telephone, adigital music and/or video player, and so on. As also illustrated, thesystem includes a plurality of moveable feet 102 a-102 d, each of themoveable feet including a force sensor 103 a-103 d.

As can be seen from FIG. 1, the moveable feet 102 a-102 d are positionedsuch that they are operable to support the electronic device 101 whenthe electronic device is placed on one or more surfaces, such as atable, a desk, a lap, and so on. When force is exerted on the electronicdevice, the force may be measured by one or more of the force sensors103 a-103 d as force data.

For example, when a user presses down on a portion of the electronicdevice 101, one or more of the force sensors 103 a-103 d may measure theforce of the user's press as force data. By comparing force data fromthe various force sensors, the location where the user exerted force maybe determined (as the detected force may be greater closer to where theuser pressed down, and closer to a particular force sensor, and may belesser further from where the user pressed down, and closer to adifferent force sensor). By comparing current force data with previousforce data, movement of a user's touch across the electronic device maybe determinable.

However, forces other than those exerted by a user may also be detected.For example, if the moveable feet 102 a-102 d support the electronicdevice 101 on a surface, the weight of the electronic device itself mayexert a force that is detectable by the force sensors 103 a-103 d.

FIG. 2 is a side cross sectional view of a portion of the electronicdevice 101 of the system of FIG. 1 taken along the line 2-2 in FIG. 1.As illustrated, the moveable foot 102 a is operable to move in and/orout of a cavity 105 of the electronic device 101 via an aperture 106 inresponse to force exerted on the electronic device. As the moveable footmoves in and/or out of the cavity, the force sensor 103 a measures thechange in force as force data.

FIG. 3 illustrates a side plan view illustrating another force sensor303 that may be utilized in various other implementations. Asillustrated, the force sensor includes a positive capacitance plate 304separated from a negative capacitance plate 306 by a flexible member 305(which may be composed of silicone and/or another flexible material).When force is exerted on the force sensor, the flexible member may flex,allowing the positive and negative capacitance plates to move closer toand/or further from each other. Changes in capacitance related to theposition of the positive and negative capacitance plates may detectedand utilized to generate data regarding the force exerted on the forcesensor.

Returning to FIG. 2, as illustrated, in some cases the cavity may belined with a material 104, which may be rigid in some implementations.

Returning to FIG. 1, when force data is measured by one or more of theforce sensors 103 a-103 d, the force data may be interpreted as one ormore inputs. Such inputs may be one or more navigational instructions,one or more instructions for one or more applications currentlyexecuting on the electronic device 101, and so on. In someimplementations, the input which the force data is interpreted as may beuser configurable.

For example, when force data is received, the force data may beinterpreted as directional and/or other navigational information. Bycomparing force data from the various force sensors 103 a-103 d, thelocation where force was exerted may be determined (as the detectedforce may be greater closer to where a user pressed down, and closer toa particular force sensor, and may be lesser further from where a userpressed down, and closer to a different force sensor). By comparingcurrent force data with previous force data, movement of a touch acrossthe electronic device may be determinable. In some cases, the force datamay be interpreted similar to the arrow keys of a keyboard (such aspressure near the top of the electronic device 101 corresponds to an ‘uparrow’ input and so on).

Further, in some cases the electronic device may have one or moredifferent statuses. For example, a laptop computer may include a lid andmay have a closed lid status and an open lid status. The laptop computermay also have an active state and one or more inactive states (such as asleep state, a hibernate state, a standby state, and so on). Further,the laptop computer may have an ‘on table’ state when the laptop ispositioned on a table or other even surface and an ‘elevated state’ whenthe laptop is positioned on an uneven surface such as a lap (which maybe detectable by comparing differing force data from various of theforce sensors 103 a-103 d).

In various cases, the status of the electronic device 101 may be acombination of one or more different statuses. For example, a laptopcomputer may simultaneously have a closed lid status or an open lidstatus, an active status or one or more inactive statuses, and an ontable or elevated status. In such a case, the laptop computer may havean open lid/active/on table status at a particular point in time. It isunderstood that the sample statuses provided above are examples and anelectronic device may have any number of different statuses (orcombinations of statuses) at a given time.

In cases where the electronic device 101 has different statuses (orcombinations of statuses), the status of the electronic device may bedetermined. The input which the force data is interpreted may thendiffer depending on the status of the electronic device.

For example, when force data is received when a laptop is open and auser is currently active, the force data may be interpreted asdirectional and/or other navigational information. By comparing forcedata from the various force sensors, the location where force wasexerted may be determined (as the detected force may be greater closerto where a user pressed down, and closer to a particular force sensor,and may be lesser further from where a user pressed down, and closer toa different force sensor). By comparing current force data with previousforce data, movement of a touch across the electronic device may bedeterminable. In some cases, the force data may be interpreted similarto the arrow keys of a keyboard (such as pressure near the top of thelaptop corresponds to an ‘up arrow’ input and so on).

By way of another example, when force data is received when a laptop isopen and no user is currently active, the force data may be interpretedas an instruction to switch the computer between active and inactivestates or between various inactive states (such as switching an activelaptop computer to a sleep mode, switching a sleeping laptop computer toa hibernate mode, and so on).

By way of a third example, when force data is received when a laptop isclosed and an application is currently executing on the laptop computer,the force data may be interpreted as an instruction to the application.In a first case, the application may be a presentation software programand the instruction may include a command to switch the slide currentlybeing presented (such as advancing to the next slide and/or returning toa previous slide) via one or more projectors and/or other output devicesconnected to the laptop. In such a case, a user may manipulate thepresentation software during a presentation while the laptop is closedby pressing on the top of the laptop.

In a second case, the application may be a music player program and theinstruction may include a command to alter the music currently beingpresented (such as fast forwarding the music, rewinding the music,speeding up the music, slowing down the music, and so on) via one ormore speakers and/or other output devices and/or components. In such acase, a user may manipulate the music player program while the laptop isclosed and the music player program is playing music by pressing on thetop of the laptop.

By way of a fourth example, force data may be received indicating that alaptop computer is on a lap as opposed to an even surface such as atable. Such force may not correspond to force exerted by a user, but theforce may be interpreted as a command to engage a cooling mechanism ofthe laptop such that the laptop does not reach a temperature that isuncomfortable for a user's lap. As such, in various cases, the forcedata itself may be utilized to determine a status of the electronicdevice, the determination of which may then be utilized to interpret theforce data as one or more particular inputs.

In any of the above examples, differing force data may correspond todiffering inputs in a variety of ways. In some cases, force data may beinterpreted as a first input when the force is above a threshold and asa second input when the force is below threshold. In other cases, forcedata may be interpreted as a first input when the force is exerted on afirst location of the electronic device 101 and as a second input whenthe force is exerted on a second location of the electronic device. Itis understood that various configurations are possible without departingfrom the scope of the present disclosure. Further, in various cases theinput as which the force data is interpreted may be user configurable.

FIG. 4 illustrates a first example method 400 for controlling electronicdevices using force sensors. The method 400 may be performed by thesystem 100 of FIG. 1. The flow begins at block 401 and proceeds to block402 where an electronic device operates. The flow then proceeds to block403 where it is determined whether or not force data is received fromone or more force sensors. If so, the flow proceeds to block 404.Otherwise, the flow returns to block 402 where the electronic devicecontinues to operate.

At block 404, the force data is interpreted to determine one or moreinputs that correspond to the force data. In some cases, thedetermination of which input to determine the force data as may bedependent on the force data and/or one or more determined statuses ofthe electronic device.

The flow then proceeds to block 405 where the electronic deviceprocessed the determined input. Finally, the flow returns to block 402where the electronic device continues to operate.

Although the method 400 is illustrated and described above as includingparticular operations performed in a particular order, it is understoodthat this is for the purposes of example. In other implementations,different orders of the same and/or different operations may beperformed without departing from the scope of the present disclosure.For example, in one or more implementations, an operation oftransmitting the determined input to the electronic device may beperformed between blocks 404 and 405.

FIG. 5 illustrates a second example method 500 for controllingelectronic devices using force sensors. The method 500 may be performedby the system 100 of FIG. 1. The flow begins at block 501 and proceedsto block 502 where an electronic device operates. The flow then proceedsto block 503 where it is determined whether or not force data isreceived from one or more force sensors. If so, the flow proceeds toblock 504. Otherwise, the flow returns to block 502 where the electronicdevice continues to operate.

At block 504, it is determined whether or not the electronic device hasan ‘open’ status. If so, the flow proceeds to block 505. Otherwise, theflow proceeds to block 508.

At block 505, after it is determined that the electronic device has anopen status, it is determine whether or not the electronic device has a‘not elevated’ status. If so, the flow proceeds to block 511. Otherwise,the flow proceeds to block 506.

At block 506, after it is determined that the electronic device has an‘elevated’ status, the force data is interpreted to determine one ormore inputs that correspond to the force data based on a combined openstatus and an elevated status. The flow then proceeds to block 507 wherethe determined input is processed before the flow returns to block 502and the electronic device continues to operate.

At block 511, after it is determined that the electronic device has anot elevated status, the force data is interpreted to determine one ormore inputs that correspond to the force data based on a combined openstatus and a not elevated status. The flow then proceeds to block 507where the determined input is processed before the flow returns to block502 and the electronic device continues to operate.

At block 508, after it is determined that the electronic device has a‘closed’ status, it is determine whether or not the electronic devicehas an elevated status. If so, the flow proceeds to block 509.Otherwise, the flow proceeds to block 510.

At block 509, after it is determined that the electronic device has an‘elevated’ status, the force data is interpreted to determine one ormore inputs that correspond to the force data based on a combined closedstatus and an elevated status. The flow then proceeds to block 507 wherethe determined input is processed before the flow returns to block 502and the electronic device continues to operate.

At block 510, after it is determined that the electronic device has anot elevated status, the force data is interpreted to determine one ormore inputs that correspond to the force data based on a combined closedstatus and a not elevated status. The flow then proceeds to block 507where the determined input is processed before the flow returns to block502 and the electronic device continues to operate.

Although the method 500 is illustrated and described above as includingparticular operations performed in a particular order, it is understoodthat this is for the purposes of example. In other implementations,different orders of the same and/or different operations may beperformed without departing from the scope of the present disclosure.For example, in one or more implementations, various statuses of theelectronic device other than open, closed, elevated, and/or not elevatedmay be determined and the force data may be interpreted as variousinputs depending on the determined statuses.

Returning to FIG. 1, as illustrated, the force sensors 103 a-103 d areincorporated into the electronic device 101. However, it is understoodthat this is an example. In various cases, the force sensors may beincorporated into the electronic device and/or incorporated into adevice that is external to the electronic device without departing fromthe present disclosure. In cases where the force sensors areincorporated into the electronic device, the electronic device mayinclude one or more processing units that receive and interpret forcedata from the force sensors.

However, in cases where the force sensors 103 a-103 d are incorporatedinto a device that is external to the electronic device 101, either theexternal device and/or the electronic device may include one or moreprocessing units that receive and interpret force data from the forcesensors. In such cases where the external device includes the one ormore processing units, the input as which the force data is interpretedmay be communicated by the external device to the electronic device.However, in cases where the electronic device includes the one or moreprocessing units, the external device may communicate the force data tothe one or more processing units of the electronic device forinterpretation.

For example, in some implementations, the force sensors 103 a-103 d maybe incorporated into an external track pad or other external inputdevice that is separate from the electronic device 101. Such an externaltrack pad may include a plate or other housing that is operable to besupported on one or more surfaces by the moveable feet 102 a-102 d thatinclude the force sensors. When force data is received, the force datamay be interpreted as directional and/or other navigational information(whether by a processing unit of the external track pad or by sendingthe force data to a processing unit of the electronic device). Bycomparing force data from the various force sensors 103 a-103 d of theexternal track pad, the location where force was exerted on the externaltrack pad may be determined (as the detected force may be greater closerto where a user pressed down, and closer to a particular force sensor,and may be lesser further from where a user pressed down, and closer toa different force sensor). By comparing current force data with previousforce data, movement of a touch across the external track pad may bedeterminable. In some cases, the force data may be interpreted similarto the arrow keys of a keyboard (such as pressure near the top of theexternal track pad corresponds to an ‘up arrow’ input and so on).

Further, although the system 100 is illustrated and described above asincluding four moveable feet 102 a-102 d and four force sensors 103a-103 d, it is understood that this is for the purposes of example. Invarious implementations, any number of moveable feet and/or forcesensors may be used in a variety of different configurations in order topotentially support the electronic device 101 (and/or external device inwhich the moveable feet and/or force sensors are incorporated into) onone or more surfaces without departing from the scope of the presentdisclosure.

Additionally, although the system 100 is illustrated and described aboveas including four moveable feet 102 a-102 d and four force sensors 103a-103 d located in the moveable feet, it is understood that this is forthe purposes of example. In various implementations, moveable feet orother structures operable to support the electronic device on one ormore surfaces may not be utilized. Instead, force sensors may be locatedin such embodiments in a bottom portion of the electronic device, a topportion of the electronic device, a hinge between a lid and base of theelectronic device, a specific portion of the electronic device, and soon without departing from the scope of the present disclosure.

FIG. 6 shows a conceptual drawing of communication between a touch I/Odevice and a computing system that may be utilized in variousimplementations of the present disclosure. FIG. 7 shows a conceptualdrawing of a system force sensors that may be utilized in variousimplementations of the present disclosure.

Described embodiments may include touch I/O device 1001 that can receivetouch input and force input (such as possibly including touch locationsand applied force at those locations) for interacting with computingsystem 1003 (such as shown in the FIG. 6) via wired or wirelesscommunication channel 1002. Touch I/O device 1001 may be used to provideuser input to computing system 1003 in lieu of or in combination withother input devices such as a keyboard, mouse, or possibly otherdevices. In alternative embodiments, touch I/O device 1001 may be usedin conjunction with other input devices, such as in addition to or inlieu of a mouse, trackpad, or possibly another pointing device. One ormore touch I/O devices 1001 may be used for providing user input tocomputing system 1003. Touch I/O device 1001 may be an integral part ofcomputing system 1003 (e.g., touch screen on a laptop) or may beseparate from computing system 1003.

Touch I/O device 1001 may include a touch sensitive and/or forcesensitive panel which is wholly or partially transparent,semitransparent, non-transparent, opaque or any combination thereof.Touch I/O device 1001 may be embodied as a touch screen, touch pad, atouch screen functioning as a touch pad (e.g., a touch screen replacingthe touchpad of a laptop), a touch screen or touchpad combined orincorporated with any other input device (e.g., a touch screen ortouchpad disposed on a keyboard, disposed on a trackpad or otherpointing device), any multi-dimensional object having a touch sensitivesurface for receiving touch input, or another type of input device orinput/output device.

In one example, touch I/O device 1001 embodied as a touch screen mayinclude a transparent and/or semitransparent touch sensitive and forcesensitive panel at least partially or wholly positioned over at least aportion of a display. (Although the touch sensitive and force sensitivepanel is described as at least partially or wholly positioned over atleast a portion of a display, in alternative embodiments, at least aportion of circuitry or other elements used in embodiments of the touchsensitive and force sensitive panel may be at least positioned partiallyor wholly positioned under at least a portion of a display, interleavedwith circuits used with at least a portion of a display, or otherwise.)According to this embodiment, touch I/O device 1001 functions to displaygraphical data transmitted from computing system 1003 (and/or anothersource) and also functions to receive user input. In other embodiments,touch I/O device 1001 may be embodied as an integrated touch screenwhere touch sensitive and force sensitive components/devices areintegral with display components/devices. In still other embodiments atouch screen may be used as a supplemental or additional display screenfor displaying supplemental or the same graphical data as a primarydisplay and to receive touch input, including possibly touch locationsand applied force at those locations.

Touch I/O device 1001 may be configured to detect the location of one ormore touches or near touches on device 1001, and where applicable, forceof those touches, based on capacitive, resistive, optical, acoustic,inductive, mechanical, chemical, or electromagnetic measurements, inlieu of or in combination or conjunction with any phenomena that can bemeasured with respect to the occurrences of the one or more touches ornear touches, and where applicable, force of those touches, in proximityto device 1001. Software, hardware, firmware or any combination thereofmay be used to process the measurements of the detected touches, andwhere applicable, force of those touches, to identify and track one ormore gestures. A gesture may correspond to stationary or non-stationary,single or multiple, touches or near touches, and where applicable, forceof those touches, on touch I/O device 1001. A gesture may be performedby moving one or more fingers or other objects in a particular manner ontouch I/O device 1001 such as tapping, pressing, rocking, scrubbing,twisting, changing orientation, pressing with varying pressure and thelike at essentially the same time, contiguously, consecutively, orotherwise. A gesture may be characterized by, but is not limited to apinching, sliding, swiping, rotating, flexing, dragging, tapping,pushing and/or releasing, or other motion between or with any otherfinger or fingers, or any other portion of the body or other object. Asingle gesture may be performed with one or more hands, or any otherportion of the body or other object by one or more users, or anycombination thereof.

Computing system 1003 may drive a display with graphical data to displaya graphical user interface (GUI). The GUI may be configured to receivetouch input, and where applicable, force of that touch input, via touchI/O device 1001. Embodied as a touch screen, touch I/O device 1001 maydisplay the GUI. Alternatively, the GUI may be displayed on a displayseparate from touch I/O device 1001. The GUI may include graphicalelements displayed at particular locations within the interface.Graphical elements may include but are not limited to a variety ofdisplayed virtual input devices including virtual scroll wheels, avirtual keyboard, virtual knobs or dials, virtual buttons, virtuallevers, any virtual UI, and the like. A user may perform gestures at oneor more particular locations on touch I/O device 1001 which may beassociated with the graphical elements of the GUI. In other embodiments,the user may perform gestures at one or more locations that areindependent of the locations of graphical elements of the GUI. Gesturesperformed on touch I/O device 1001 may directly or indirectlymanipulate, control, modify, move, actuate, initiate or generally affectgraphical elements such as cursors, icons, media files, lists, text, allor portions of images, or the like within the GUI. For instance, in thecase of a touch screen, a user may directly interact with a graphicalelement by performing a gesture over the graphical element on the touchscreen. Alternatively, a touch pad generally provides indirectinteraction. Gestures may also affect non-displayed GUI elements (e.g.,causing user interfaces to appear) or may affect other actions withincomputing system 1003 (e.g., affect a state or mode of a GUI,application, or operating system). Gestures may or may not be performedon touch I/O device 1001 in conjunction with a displayed cursor. Forinstance, in the case in which gestures are performed on a touchpad, acursor (or pointer) may be displayed on a display screen or touch screenand the cursor may be controlled via touch input, and where applicable,force of that touch input, on the touchpad to interact with graphicalobjects on the display screen. In other embodiments in which gesturesare performed directly on a touch screen, a user may interact directlywith objects on the touch screen, with or without a cursor or pointerbeing displayed on the touch screen.

Feedback may be provided to the user via communication channel 1002 inresponse to or based on the touch or near touches, and where applicable,force of those touches, on touch I/O device 1001. Feedback may betransmitted optically, mechanically, electrically, olfactory,acoustically, haptically, or the like or any combination thereof and ina variable or non-variable manner.

Attention is now directed towards embodiments of a system architecturethat may be embodied within any portable or non-portable deviceincluding but not limited to a communication device (e.g. mobile phone,smart phone), a multi-media device (e.g., MP3 player, TV, radio), aportable or handheld computer (e.g., tablet, netbook, laptop), a desktopcomputer, an All-In-One desktop, a peripheral device, or any other(portable or non-portable) system or device adaptable to the inclusionof system architecture 2000, including combinations of two or more ofthese types of devices. FIG. 7 shows a block diagram of one embodimentof system 2000 that generally includes one or more computer-readablemediums 2001, processing system 2004, Input/Output (I/O) subsystem 2006,electromagnetic frequency circuitry, such as possibly radio frequency(RF) or other frequency circuitry 2008 and audio circuitry 2010. Thesecomponents may be coupled by one or more communication buses or signallines 2003. Each such bus or signal line may be denoted in the form2003-X, where X can be a unique number. The bus or signal line may carrydata of the appropriate type between components; each bus or signal linemay differ from other buses/lines, but may perform generally similaroperations.

It should be apparent that the architecture shown in FIG. 6 and FIG. 7is only one example architecture of system 2000, and that system 2000could have more or fewer components than shown, or a differentconfiguration of components. The various components shown in FIGS. 1-3can be implemented in hardware, software, firmware or any combinationthereof, including one or more signal processing and/or applicationspecific integrated circuits.

RF circuitry 2008 is used to send and receive information over awireless link or network to one or more other devices and includeswell-known circuitry for performing this function. RF circuitry 2008 andaudio circuitry 2010 are coupled to processing system 2004 viaperipherals interface 2016. Interface 2016 includes various knowncomponents for establishing and maintaining communication betweenperipherals and processing system 2004. Audio circuitry 2010 is coupledto audio speaker 2050 and microphone 2052 and includes known circuitryfor processing voice signals received from interface 2016 to enable auser to communicate in real-time with other users. In some embodiments,audio circuitry 2010 includes a headphone jack (not shown).

Peripherals interface 2016 couples the input and output peripherals ofthe system to processor 2018 and computer-readable medium 2001. One ormore processors 2018 communicate with one or more computer-readablemediums 2001 via controller 2020. Computer-readable medium 2001 can beany device or medium that can store code and/or data for use by one ormore processors 2018. Medium 2001 can include a memory hierarchy,including but not limited to cache, main memory and secondary memory.The memory hierarchy can be implemented using any combination of RAM(e.g., SRAM, DRAM, DDRAM), ROM, FLASH, magnetic and/or optical storagedevices, such as disk drives, magnetic tape, CDs (compact disks) andDVDs (digital video discs). Medium 2001 may also include a transmissionmedium for carrying information-bearing signals indicative of computerinstructions or data (with or without a carrier wave upon which thesignals are modulated). For example, the transmission medium may includea communications network, including but not limited to the Internet(also referred to as the World Wide Web), intranet(s), Local AreaNetworks (LANs), Wide Local Area Networks (WLANs), Storage Area Networks(SANs), Metropolitan Area Networks (MAN) and the like.

One or more processors 2018 run various software components stored inmedium 2001 to perform various functions for system 2000. In someembodiments, the software components include operating system 2022,communication module (or set of instructions) 2024, touch and appliedforce processing module (or set of instructions) 2026, graphics module(or set of instructions) 2028, one or more applications (or set ofinstructions) 2030, and force sensing module (or set of instructions)2038. Each of these modules and above noted applications correspond to aset of instructions for performing one or more functions described aboveand the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwiserearranged in various embodiments. In some embodiments, medium 2001 maystore a subset of the modules and data structures identified above.Furthermore, medium 2001 may store additional modules and datastructures not described above.

Operating system 2022 includes various procedures, sets of instructions,software components and/or drivers for controlling and managing generalsystem tasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 2024 facilitates communication with other devicesover one or more external ports 2036 or via RF circuitry 2008 andincludes various software components for handling data received from RFcircuitry 2008 and/or external port 2036.

Graphics module 2028 includes various known software components forrendering, animating and displaying graphical objects on a displaysurface. In embodiments in which touch I/O device 2012 is a touchsensitive and force sensitive display (e.g., touch screen), graphicsmodule 2028 includes components for rendering, displaying, and animatingobjects on the touch sensitive and force sensitive display.

One or more applications 2030 can include any applications installed onsystem 2000, including without limitation, a browser, address book,contact list, email, instant messaging, word processing, keyboardemulation, widgets, JAVA-enabled applications, encryption, digitalrights management, voice recognition, voice replication, locationdetermination capability (such as that provided by the globalpositioning system, also sometimes referred to herein as “GPS”), a musicplayer, and otherwise.

Touch and applied force processing module 2026 includes various softwarecomponents for performing various tasks associated with touch I/O device2012 including but not limited to receiving and processing touch inputand applied force input received from I/O device 2012 via touch I/Odevice controller 2032.

System 2000 may further include force sensing module 2038 for performingforce sensing.

I/O subsystem 2006 is coupled to touch I/O device 2012 and one or moreother I/O devices 2014 for controlling or performing various functions.Touch I/O device 2012 communicates with processing system 2004 via touchI/O device controller 2032, which includes various components forprocessing user touch input and applied force input (e.g., scanninghardware). One or more other input controllers 2034 receives/sendselectrical signals from/to other I/O devices 2014. Other I/O devices2014 may include physical buttons, dials, slider switches, sticks,keyboards, touch pads, additional display screens, or any combinationthereof.

If embodied as a touch screen, touch I/O device 2012 displays visualoutput to the user in a GUI. The visual output may include text,graphics, video, and any combination thereof. Some or all of the visualoutput may correspond to user-interface objects. Touch I/O device 2012forms a touch-sensitive and force-sensitive surface that accepts touchinput and applied force input from the user. Touch I/O device 2012 andtouch screen controller 2032 (along with any associated modules and/orsets of instructions in medium 2001) detects and tracks touches or neartouches, and where applicable, force of those touches (and any movementor release of the touch, and any change in the force of the touch) ontouch I/O device 2012 and converts the detected touch input and appliedforce input into interaction with graphical objects, such as one or moreuser-interface objects. In the case in which device 2012 is embodied asa touch screen, the user can directly interact with graphical objectsthat are displayed on the touch screen. Alternatively, in the case inwhich device 2012 is embodied as a touch device other than a touchscreen (e.g., a touch pad or trackpad), the user may indirectly interactwith graphical objects that are displayed on a separate display screenembodied as I/O device 2014.

Touch I/O device 2012 may be analogous to the multi-touch sensitivesurface described in the following U.S. Pat. No. 6,323,846 (Westerman etal.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No.6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1,each of which is hereby incorporated by reference.

Embodiments in which touch I/O device 2012 is a touch screen, the touchscreen may use LCD (liquid crystal display) technology, LPD (lightemitting polymer display) technology, OLED (organic LED), or OEL(organic electro luminescence), although other display technologies maybe used in other embodiments.

Feedback may be provided by touch I/O device 2012 based on the user'stouch, and applied force, input as well as a state or states of what isbeing displayed and/or of the computing system. Feedback may betransmitted optically (e.g., light signal or displayed image),mechanically (e.g., haptic feedback, touch feedback, force feedback, orthe like), electrically (e.g., electrical stimulation), olfactory,acoustically (e.g., beep or the like), or the like or any combinationthereof and in a variable or non-variable manner.

System 2000 also includes power system 2044 for powering the varioushardware components and may include a power management system, one ormore power sources, a recharging system, a power failure detectioncircuit, a power converter or inverter, a power status indicator and anyother components typically associated with the generation, managementand distribution of power in portable devices.

In some embodiments, peripherals interface 2016, one or more processors2018, and memory controller 2020 may be implemented on a single chip,such as processing system 2004. In some other embodiments, they may beimplemented on separate chips.

In one embodiment, an example system includes a force sensor coupled tothe touch I/O device 2012, such as coupled to a force sensor controller.For example, the force sensor controller can be included in the I/Osubsystem 2006. The force sensor controller can be coupled to aprocessor or other computing device, such as the processor 2018 or thesecure processor 2040, with the effect that information from the forcesensor controller can be measured, calculated, computed, or otherwisemanipulated. In one embodiment, the force sensor can make use of one ormore processors or other computing devices, coupled to or accessible tothe touch I/O device 2012, such as the processor 2018, the secureprocessor 2040, or otherwise. In alternative embodiments, the forcesensor can make use of one or more analog circuits or other specializedcircuits, coupled to or accessible to the touch I/O device 2012, such asmight be coupled to the I/O subsystem 2006. It should be appreciatedthat many of the components described herein may be optional and omittedin some embodiments, such as the secure processor 2040, or combined,such as the processor and secure processor. The same is generally truefor all figures described herein.

As discussed above and as illustrated in the accompanying figures, thepresent disclosure discloses systems and methods for controllingelectronic devices using force sensors. A plurality of force sensors maybe configured such that they are operable to support one or morehousings on one or more surfaces. When force is exerted on the housing,this force may be measured by the force sensors as force data. Thisforce data may be interpreted (such as by one or more processing units)as at least one input for an electronic device. In some implementations,the electronic device may include various different statuses. In suchimplementations, the status of the electronic device may be determinedand the input that the force data is interpreted as may depend on thedetermined status of the electronic device. In this way, an input devicethat may not require extensive hardware, special surfaces, and/or othercostly components may be provided. Further, such an input device mayenable the electronic device itself to be utilized as an input device.

In the present disclosure, the methods disclosed may be implemented assets of instructions or software readable by a device. Further, it isunderstood that the specific order or hierarchy of steps in the methodsdisclosed are examples of sample approaches. In other embodiments, thespecific order or hierarchy of steps in the method can be rearrangedwhile remaining within the disclosed subject matter. The accompanyingmethod claims present elements of the various steps in a sample order,and are not necessarily meant to be limited to the specific order orhierarchy presented.

The described disclosure may be provided as a computer program product,or software, that may include a non-transitory machine-readable mediumhaving stored thereon instructions, which may be used to program acomputer system (or other electronic devices) to perform a processaccording to the present disclosure. A non-transitory machine-readablemedium includes any mechanism for storing information in a form (e.g.,software, processing application) readable by a machine (e.g., acomputer). The non-transitory machine-readable medium may take the formof, but is not limited to, a magnetic storage medium (e.g., floppydiskette, video cassette, and so on); optical storage medium (e.g.,CD-ROM); magneto-optical storage medium; read only memory (ROM); randomaccess memory (RAM); erasable programmable memory (e.g., EPROM andEEPROM); flash memory; and so on.

It is believed that the present disclosure and many of its attendantadvantages will be understood by the foregoing description, and it willbe apparent that various changes may be made in the form, constructionand arrangement of the components without departing from the disclosedsubject matter or without sacrificing all of its material advantages.The form described is merely explanatory, and it is the intention of thefollowing claims to encompass and include such changes.

While the present disclosure has been described with reference tovarious embodiments, it will be understood that these embodiments areillustrative and that the scope of the disclosure is not limited tothem. Many variations, modifications, additions, and improvements arepossible. More generally, embodiments in accordance with the presentdisclosure have been described in the context or particular embodiments.Functionality may be separated or combined in blocks differently invarious embodiments of the disclosure or described with differentterminology. These and other variations, modifications, additions, andimprovements may fall within the scope of the disclosure as defined inthe claims that follow.

We claim:
 1. A method for controlling electronic devices using forcesensors, the method comprising: receiving force data, utilizing at leastone processing unit, from a plurality of force sensors each connected toone of a number of movable feet that are operable to support at leastone housing on at least one surface wherein each of the plurality offorce sensors detects a capacitive change between a pair of capacitiveplates separated by flexible material that is compressed by movement ofthe respective one of the number of moveable feet; and interpreting,utilizing the at least one processing unit, the force data as: at leastone first type of input for an electronic device when the at least oneprocessing unit determines that an input device other than the pluralityof force sensors is available; and at least one second type of input forthe electronic device when the at least one processing unit determinesthat the input device is unavailable.
 2. The method of claim 1, whereinsaid operation of interpreting, utilizing the at least one processingunit, the force data as at least one first type of input for anelectronic device further comprises comparing data from at least onefirst force sensor of the plurality of force sensors with data from atleast one second force sensor of the plurality of force sensors todetermine at least one navigational instruction.
 3. The method of claim1, further comprising determining a status of the electronic device,wherein said operation of interpreting, utilizing the at least oneprocessing unit, the force data as at least one first type of input foran electronic device further comprises interpreting the force data as atleast one first input of the first type of input when the status is afirst status and as at least one second input of the first type of inputwhen the status is a second status.
 4. The method of claim 3, whereinthe first status corresponds at least to the at least one housing beingpositioned on the at least one surface and the second status correspondsat least to the at least one housing not being positioned on the atleast one surface.
 5. The method of claim 1, wherein the determinationthat the input device is unavailable corresponds at least to a closedlid of the electronic device and the determination that the input deviceis available corresponds at least to an open lid of the electronicdevice.
 6. The method of claim 3, wherein the first status correspondsat least to an active status and the second status corresponds at leastto at least one inactive status.
 7. The method of claim 3, wherein thefirst status corresponds at least to a program executing on theelectronic device and the second status corresponds at least to theprogram not executing on the electronic device.
 8. The method of claim1, wherein the at least one first type of input comprises at least oneinstruction for at least one application executing on the electronicdevice.
 9. A system for controlling electronic devices using forcesensors comprising: at least one housing; a plurality of force sensorseach connected to one of a number of movable feet that are operable tosupport the at least one housing on at least one surface; and at leastone processing unit, communicably coupled to the plurality of forcesensors that interprets force data received from at least one of theplurality of force sensors as at least one first kind of input for anelectronic device when the at least one processing unit determines thatan input device other than the plurality of force sensors is availableand at least one second kind of input for the electronic device when theat least one processing unit determines that the input device isunavailable.
 10. The system of claim 9, wherein the at least oneprocessing unit determines a status of the electronic device andinterprets force data received from at least one of the plurality offorce sensors as at least one first input of the first kind of inputwhen the status is a first status and as at least one second input ofthe first kind of input when the status is a second status.
 11. Thesystem of claim 9, wherein the determination that the input device isunavailable corresponds at least to a closed lid of the electronicdevice and the determination that the input device is availablecorresponds at least to an open lid of the electronic device.
 12. Thesystem of claim 10, wherein the first status corresponds at least to anactive status and the second status corresponds at least to at least oneinactive status.
 13. The system of claim 10, wherein the first statuscorresponds at least to a program executing on the electronic device andthe second status corresponds at least to the program not executing onthe electronic device.
 14. The system of claim 10, wherein the firststatus corresponds at least to the at least one housing being positionedon the at least one surface and the second status corresponds at leastto the at least one housing not being positioned on the at least onesurface.
 15. The system of claim 9, wherein the at least one housing isincorporated into the electronic device.
 16. The system of claim 9,wherein the at least one housing is external to the electronic device.17. The system of claim 16, wherein the at least one processing unit isincorporated into the electronic device.
 18. The system of claim 9,wherein the at least one first kind of input comprises at least onenavigational instruction.
 19. The system of claim 9, wherein the atleast one first kind of input comprises at least one instruction for atleast one application executing on the electronic device.
 20. Anelectronic device, comprising: at least one housing; a plurality offorce sensors each connected to one of a number of movable feet that areoperable to support the at least one housing on at least one surface andeach detecting force caused by movement of the respective one of thenumber of moveable feet; an input device other than the plurality offorce sensors; and at least one processing unit, communicably coupled tothe plurality of force sensors that determines a status of theelectronic device, the status relating to whether or not the inputdevice is available, and interprets force data received from at leastone of the plurality of force sensors as at least one first input whenthe status is a first status and as at least one second input when thestatus is a second status.